Tracking driving without mobile phone distraction

ABSTRACT

A mobile communication device has a plurality of modes, including a normal mode and a driving mode. In the driving mode, one or more features of said device are at least partially disabled, including one or more features relating to communication supported by the device. The device tracks particular information about the device&#39;s modes and reports some of the particular information to at least one location off the device. The particular information about said device&#39;s modes is usable to determine when the device was in driving mode.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/589,518, filed May 8, 2017, issued as U.S. Pat. No. 9,781,250 on Oct.3, 2017, which is a continuation of U.S. patent application Ser. No.15/168,196, filed May 30, 2016, titled “Methods, Devices and SystemsSupporting Driving and Studying without Distraction,” issued as U.S.Pat. No. 9,699,301 on Jul. 4, 2017 and which claims priority from U.S.Provisional Patent Application No. 62/168,899, filed May 31, 2015, theentire contents of each of which are hereby fully incorporated herein byreference for all purposes. Application Ser. No. 15/168,196 is also acontinuation of U.S. patent application Ser. No. 15/589,518, filed, May8, 2017, the entire contents of which are hereby fully incorporatedherein by reference for all purposes. U.S. patent application Ser. No.15/589,518 is a continuation of U.S. patent application Ser. No.15/168,196, which claims priority from U.S. Provisional PatentApplication No. 62/168,899.

COPYRIGHT STATEMENT

This patent document contains material subject to copyright protection.The copyright owner has no objection to the reproduction of this patentdocument or any related materials in the files of the United StatesPatent and Trademark Office, but otherwise reserves all copyrightswhatsoever.

BACKGROUND OF THE INVENTION Field of the Invention

This invention relates to controlling the use of computer devices, and,more particularly to systems, methods and devices to control use ofcomputer devices for periods of time in order to avoid distractions.

Background

Mobile devices such as mobile or cell phones, laptop computers, and thelike are ubiquitous, and their use among teenagers and young adults hasbecome widespread. Many teenagers use mobile phones almost all the time.The devices are used for all sorts of reasons, e.g., to communicate withfriends, teachers, family, etc., to access social network sites (e.g.,Facebook®, Twitter®, etc.), to listen to music, to watch videos, etc.Mobile computing devices have permeated teenagers' lives and theirconstant use has become a distraction. In the case of students doinghomework or studying for exams the distraction may just cause poorgrades at school. In the case of someone using a mobile computing devicewhile driving a car, the distraction may prove harmful or even fatal tothe driver and to others.

Many parents try to take away their children's mobile devices or askthem to turn them off for periods of time or while driving. And manyusers (including, especially teenagers) would like to use their mobiledevices less, especially while they are studying or doing their homeworkor driving, but the devices are sometimes quite addictive. Additionally,even when a user has decided to not use their device for a period oftime, they are often easily distracted by others contacting them viatheir devices.

It is therefore desirable and an object of the invention to provide away for a user to disable aspects of their mobile devices so that theyare not disturbed or tempted by the devices.

Other objects, features, and characteristics of the present invention aswell as the methods of operation and functions of the related elementsof structure, and the combination of parts and economies of manufacture,will become more apparent upon consideration of the followingdescription and the appended claims with reference to the accompanyingdrawings, all of which form a part of this specification.

BRIEF DESCRIPTION OF THE DRAWINGS

Various other objects, features and attendant advantages of the presentinvention will become fully appreciated as the same becomes betterunderstood when considered in conjunction with the accompanyingdrawings, provided by way of non-limiting example, in which likereference characters designate the same or similar parts throughout theseveral views, and wherein:

FIGS. 1A to 1C show aspects of computer devices on which embodiments ofthe invention operate;

FIG. 2 shows aspects of a computer devices according to exemplaryembodiments hereof;

FIG. 3 depicts states of a device according to exemplary embodimentshereof;

FIGS. 4A to 4B depict aspects of data structures according to exemplaryembodiments hereof;

FIGS. 5A to 5J are flowcharts showing operation of devices according toexemplary embodiments hereof;

FIGS. 6A to 6K are example screenshots of a aspects of a graphical userinterface according to exemplary embodiments hereof; and

FIG. 7 depicts aspects of a computer system according to exemplaryembodiments hereof.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EXEMPLARY EMBODIMENTS

Glossary

As used herein, unless used otherwise, the following terms orabbreviations have the following meanings:

API means Application Program(ing) Interface;

GUI means graphical user interface (UI);

OS means operating systems;

UI means user interface; and

UX means user experience.

A “mechanism” refers to any device(s), process(es), routine(s),service(s), or combination thereof. A mechanism may be implemented inhardware, software, firmware, using a special-purpose device, or anycombination thereof. A mechanism may be integrated into a single deviceor it may be distributed over multiple devices. The various componentsof a mechanism may be co-located or distributed. The mechanism may beformed from other mechanisms. In general, as used herein, the term“mechanism” may thus be considered to be shorthand for the termdevice(s) and/or process(es) and/or service(s).

Description

Background

As used herein the term “mobile device” refers to any device that mayconnect to other users via a communications network. A mobile device maybe a cell phone, a tablet computer, a laptop computer, a smart watch, orthe like. A mobile device may refer to devices that operate togetherwith other mobile devices (e.g., a smart watch such as Apple's iWatch®or the like, alone or in conjunction with a mobile phone such as aniPhone® or the like). The system is not limited by the manner in whichthe device connects to the network or to other devices. For example, theconnection to the network may be via a cellular network and/or via anetwork such as the Internet. It should be appreciated that aspects ofthe systems and methods described herein are not limited to mobiledevices, and that they may be applicable to any computing deviceincluding desktop computers and the like.

A typical mobile device (e.g., a smartphone or the like) is shown inFIGS. 1A to 1C.

Devices used by or in connection with embodiments hereof may be any kindof computing device, including mobile devices (e.g., phones, tablets,watches, wearable devices, etc.), computers (e.g., desktops, laptops,etc.), and the like. Each device preferably includes at least at onedisplay and at least some input mechanism. The display and inputmechanism may be separate (as in the case, e.g., of a desktop computerand detached keyboard and mouse), or integrated (as in the case, e.g.,of a tablet device such as an iPad or the like). The term “mouse” isused here to refer to any component or mechanism the may be used toposition a cursor on a display and, optionally, to interact with thecomputer. A mouse may include a touchpad that supports various gestures.A mouse may be integrated into or separate from the other parts of thedevice. A device may have multiple displays and multiple input devices.

FIGS. 1A-1C show examples of devices 100 a, 100 b, and 100 c,respectively, that may be used with or according to exemplaryembodiments hereof. Exemplary device 100 a (FIG. 1A) has an integrateddisplay and input mechanism in the form of touch screen 102. The device100 a is integrated into a single component, e.g., a smartphone, atablet computer, or the like. The device 100 a may support a software(or virtual) keyboard (VKB). Exemplary device 100 b (FIG. 1B) is alsointegrated into a single component, but, in addition to a screen 104(which may be a touch screen), the device includes a keyboard 106 and anintegrated mouse 108 (e.g., an integrated device such as a trackball ortrack pad or the like that supports movement of a cursor on the screen104). The keyboard may be a hardware keyboard (e.g., as in the case of aBlackBerry® phone). The screen 104 may be a touch screen and may supporta virtual keyboard (VKB).

The exemplary device 100 c (FIG. 1C) comprises multiple components,including a computer 110, a computer monitor or display 112, andinput/interaction mechanism(s) 114, such as, e.g., a keyboard 116 and/ora mouse 118, and/or gesture recognition mechanism 120. Although thevarious components of device 100 c are shown connected by lines in thedrawing, it should be appreciated the connection between some or all ofthe components may be wireless. Some or all of these components may beintegrated into a single physical device or appliance (e.g., a laptopcomputer), or they may all be separate components (e.g., a desktopcomputer). As another example, a device may be integrated into atelevision, an automobile dashboard, a set-top box, or the like. Thus,e.g., with reference again to FIG. 1C, the display 112 may be a displayor monitor integrated into the dashboard of an automobile and thecomputer 110 may be integrated fully or partially into the monitor. Inthis example, the input/interaction mechanisms 114 (e.g., keyboard 116and mouse 118) may be separate components connecting to the computer 110via wired and/or wireless communication (e.g., via Bluetooth® or thelike). In some cases, the input/interaction mechanisms 114 may be fullyor partially integrated into a remote control device or the like. Theseinput/interaction mechanisms 114 may use virtual keyboards generated, atleast in part, by the computer 110 on the display 112. When the deviceis used in connection with an automobile, some or all of the interactionmechanisms may be integrated with the vehicle's controls, e.g., on thesteering wheel and/or the dashboard.

It should be appreciated that these exemplary devices are shown here toaid in this description, and are not intended to limit the scope of thesystem in any way. Other devices may be used and are contemplatedherein.

FIG. 2 shows logical aspects of a typical device (e.g., 104 c, FIG. 1C),including device/client application(s)/mechanism(s) 200 interacting andoperating with device/client storage 202. Device/client storage 202 mayinclude system/administrative data 204, user data 206, planner data 208,driving data 210, and other miscellaneous/auxiliary data 212. Thedevice/client application(s)/mechanism(s) 200 may includesystem/administrative application(s)/mechanism(s) 214, user interface(UI) application(s)/mechanism(s) 216, storageapplication(s)/mechanism(s) 218, planning application(s)/mechanism(s)220, focused driving application(s)/mechanism(s) 222, and othermiscellaneous application(s)/mechanism(s) 224.

Computing devices are described in greater detail below.

The planning application(s)/mechanism(s) 220 may also be referred toherein as the planner 220 or the planner application or planner app 220.The focused driving application(s)/mechanism(s) 222 may also be referredto herein as the driving application or driving app 222 or the focuseddriving application or app 222.

The categorization of data in storage 202 is made for the purposes ofaiding this description, and those of ordinary skill in the art willrealize and appreciate, upon reading this description, that differentand/or other categorizations of the data may be used. It should also beappreciated any particular data may categorized in more than one way.Similarly, it should be appreciated that different and/or othercategorizations of the device/client application(s)/mechanism(s) 200 maybe used and furthermore, that any particular application may becategorized in more than one way.

In addition, it should be appreciated that some of theapplications/mechanisms, although shown as separate components in thedrawings, may be integrated into a single component. For example, theplanning application(s)/mechanism(s) 220 and focused drivingapplication(s)/mechanism(s) 222 may be integrated into a single focusapplication/mechanism 226, as shown by the dashed lines in FIG. 2.Similarly, the planner data 208 and the driving data 210 may beintegrated, e.g., focus data 228 as shown by the dashed lines in FIG. 2.The focus application(s)/mechanism(s) 226 may also be referred herein asthe focus application or focus app 226.

Device States

Various aspects of a device and its use may cause it to be a distractionto a user, and, depending on what the user is doing at the time of thedistraction, the distraction may be more or less harmful or dangerous.For example, it is well known that texting while driving is verydistracting and consequently very dangerous. On the other hand, textingwhile studying for a test, while distracting, may not be dangerous.

Generally, use of a device is considered a distraction when the usershould be doing something other than using the device. For example, thedevice may be a mobile phone or the like and the device may includeapplications (e.g., a chat program, a texting program, or the like) thatmay be distracting to the user. Different applications (also known as“apps”) on the device may be more or less distracting, depending on whenthey are used and on what the user is doing when they are used.

The inventor has realized that in order to reduce the distraction from acomputer device, and thereby to allow the user to focus on other tasks,it is useful, possibly necessary, to selectively block the user's accessto parts of the device. In the case of a laptop computer or the like,this blocking may involve selectively blocking the use of certain appson the device. The inventor realized that is desirable to provide a wayfor a user to disable aspects of their computers/mobile devices so thatthey are not disturbed or tempted by the devices.

In the case of a mobile phone or the like, blocking may involveselectively blocking some of the external communications aspects of thedevice. In this way the user may not only be blocked from initiating orparticipating in outgoing communications (from the device to otherusers), but may also be blocked from receiving communications (ornotifications of communications) from other users.

For the purposes of this description a device may be considered to be ina number of different states or modes. For the purposes of thisdescription the states or modes are referred to as “normal” (ornon-focused), “focused (event),” and “focused (driving)”. These threeexemplary or modes are shown in a state transition diagram in FIG. 3.Those of ordinary skill in the art will realize and appreciate, uponreading this description, that different and/or other state names may beused and that additional or fewer states may be used. For example, aparticular embodiment may only have two states: “normal” and “focused,”with no distinction between degrees of focused states.

In the “normal” state a device operates without restriction (or, atleast without restriction imposed by the focus applications.

In a “focused” mode or state, the device operates with somerestrictions. For example, in some exemplary embodiments hereof, in a“focused (event)” state or mode, the device is in a “do not disturb”mode in which the user is not notified of incoming messages or calls andin which the user cannot use various applications, make outgoing callsor send outgoing messages. Regardless of the mode, a user is neverprevented from making emergency calls. Focused modes may restrict one ormore of: some or all apps on the device; incoming and/or messages(texts, voice calls, etc.); notifications, etc.

In some embodiments, in a focused mode (e.g., drive focused or eventfocused) certain features of the user's device(s) may be modified or atleast partially disabled. These features may include one or more of: (a)at least some incoming notifications (e.g., text messages, phone calls,messages from other applications, etc.); (b) at least some outgoingcalls or messages (i.e., the ability to make at least some outgoingcalls or send outgoing messages such as text messages or the like); and(c) at least some applications on the user's device(s) (e.g., socialnetwork apps such as Facebook®, Twitter®, Snapchat®, Skype®, and thelike).

Various devices already have some form of blocking (e.g., “airplane”mode restricts all cellular communications). Preferred embodimentshereof may make use of at least some device-specific and/or built-inrestrictions.

In some exemplary embodiments hereof, the “focused (driving)” mode ismore restrictive than the “focused (event)” mode, with all device usebeing restricted (except for emergency use).

It should be appreciated that when there is more than on “focused” mode,the different “focused” modes may form a hierarchy of successively morerestricted modes. In other cases, multiple “focused” modes may bedistinct but not hierarchical.

Transition between the states/modes is discussed in greater detailbelow.

The Planner

The inventor realized that many students use planners to plan out theirdays, including, specifically, their studying and homework time. It isduring those times that people want and need to be focused, and it isduring that time that people don't want to be distracted or disturbed.The inventor realized that it would be helpful and useful to fully orpartially disable aspects of computer devices (e.g., smart phones,laptop computers, etc.) during periods when focus is required. In thisway a person need not be tempted or distracted by their devices.

Accordingly, embodiments hereof may include a planner mechanism (e.g., aplanner application 220 in FIG. 2) operating on the device. The plannermechanism interacts with data, including planner data 208, stored andmaintained in the device storage. Using the planner 220, a user is ableto set time periods during which focused attention is required (e.g.,for homework, studying, reading, etc.). The planner 220 includes a userinterface that supports entry of events and allows the user thereof toset the status of the user's devices during those events. When theplanner application 220 is running, the user may use the user interfaceto set up a plan for any period of time, although the interfacepreferably displays the events for a day.

With reference to the exemplary data structures in FIGS. 4A-4B, auser's, the planner 220 may store (in planner data 208) a series ofevents (E0, E1, E2, . . . Ej) 400, each event having an eventdescription, a device status (being the desired status of the user'sdevice(s) during the event), and an event start time. An event may havean event end time and/or a duration (the end time being computable fromthe start time and duration). In presently preferred embodiments thedevice status is either normal (corresponding to the “normal” state inFIG. 3) or “focused (event)” (corresponding to the “focus (event)” statein FIG. 3). Preferably the series of events are non-overlapping in time.

Operation of the planner 220 is described here with reference to theflowcharts in FIGS. 5A-5J.

With reference to FIG. 5A, using the user interface provided by theplanner 220, the user may set event details for any number of events.For each event the user may set an event description (e.g., “StudyFrench”), set an event start time (e.g., 4:00 PM), and set a devicestatus during the event (e.g., “Normal” or “Focused”). The defaultstatus may be either “Normal” or “Focused”, and the user is not requiredto set a device status if the default is desired. For the purposes ofthis description, an event for which the device status is set to“focused” may be referred to as a focused event, and an event for whichthe device status is set to “normal” may be referred to as a normalevent.

In preferred embodiments hereof the user's planner data 208 may beshared (e.g., via a “cloud” account) with multiple of the user'sdevices. In this manner the device status of an event may be applied tomore than one of the user's devices.

Using the user interface provided by the planner 220, the user may setthe end time or duration of an event. If the duration is set then theend time may be calculated from the start time and duration. If the userdoes not specify an end time then the planner will continue in thestatus for this event until either another event starts or the userinterrupts the planner.

The user interface of the planner 220 may provide a way (e.g., a “FOCUS”button on the screen of the device) that allows a user to selectivelyenter a focus mode without setting event data. For example, if the userselects (e.g., presses) that “FOCUS” button then the user's device(s)will go into “focused” mode. This feature may be implemented as an eventwith no description or end time, and with a start time being the time atwhich the “FOCUS” button was selected. The event may be inserted intothe user's event sequence 400. Thus, selecting the “FOCUS” buttoneffectively creates an event with no description, with the start timebeing the current time, with the device status being “focused (event)”and with no end time. The system may end “focus” mode when a userselection is made (as described below) or when another event begins. Insome embodiments the user may set a timer or duration for the “focus”mode when the button is set. As overlapping events are preferably notpermitted, an ad hoc focused event (caused by pressing the “FOCUS”button) preferably ends when the next event in the sequence begins.

The term “button,” as used herein throughout, may refer to a virtualbutton or region presented on the screen of a device by the userinterface (UI) or it may refer to a physical button of the device. Insome cases a physical device button may be set to function as anapplication-specific button while the application is running on thedevice. The terms “press” or “pressing,” when used in connection with avirtual button (e.g., one presented by the GUI), may refer to anyappropriate manner of selecting the UI region corresponding to thebutton. For example, a user may “press” a virtual (GUI) button bytouching or in some way selecting the region of the displaycorresponding to that button.

The user interface of the planner 220 may provide a way for a user toselectively terminate the current focus mode. For example, the userinterface may provide a button or the like on the screen of the devicethat, when selected by the user, causes the device to go back to“normal” mode. The planner 220 may try to discourage the user fromleaving the focus mode during an event. For example, in some embodimentsthe user may be queried about whether they really want to end the focusmode. For example, the UI may inform the user of the remaining focustime (based on the current event's end time) and ask the user if theycan wait that amount of time before leaving the focused mode. In someembodiments, if the event has an end time set, selecting the “NormalMode” (or “Un-FOCUS”) button on the user interface may cause the deviceto go into normal mode for a short period of time (e.g., 1 minute or 2minutes or 5 minutes) and then to resume in focus mode until the end ofthe event.

In some cases the user may be required to enter a code or password inorder to leave focus mode.

In operation the planner 220 traverses the user's event list 400,setting the user's device(s) to the device status corresponding to thecurrent event. With reference to the flow chart in FIG. 5B, when theplanner 220 starts, it determines (at 502) whether the current time(obtained from the device's clock) is during a planner event. This maybe determined from the start and end times of the events in the user'sevent list 400 in the focus data 228 (in planner data 208) in the devicestorage 202.

If the planner 220 determines that the current time is not within anevent then it waits until the start time of the next event or until akey or button is pressed (at 504). On the other hand, if the planner 200determines (at 502) that the current time is during a planner event(e.g., event Ek—also referred to as the current event), then (at 506)the user's device is set to the corresponding mode for that event. Thus,if the mode for the current event is “normal” then the device is set to(or left in) normal mode. If the mode for the current event is “focused”then the device is set to (or left in) focused mode.

During an event the planner 220 checks (at 508) whether the currentevent has ended. An event may end when its end time is reached. If thecurrent event has ended then the planner sets the user's device (e.g.,phone, computer, etc.) back to the non-focused (normal) mode (at 510)and then waits for the start of the next event (at 504).

If the current event has not ended the planner determines (at 512)whether a key or button on the device has been pressed. If no key orbutton has been pressed then the planner 220 repeats the “end of event”check (at 508). If the planner 220 determines that a key or button hasbeen pressed then the planner processes that key/button press (at 514).

As described, the planner 220 may process a button press while idle(i.e., while waiting for an event at 504) or during an event (at 514).In either case, the current device mode or status may be normal orfocused. With reference to the flowchart in FIG. 5C, when a button ispressed the planner 220 processes that press (at 514) by firstdetermining the current device mode (at 516). If the current mode is“normal” (i.e., non-focused) then the planner 220 processes the currentkey/button while in normal mode (at 518), otherwise, if the current modeis “focused” then the planner 220 processes the current key/button whilein the focused mode (at 520).

For the processing when the current mode is “normal” (at 518), if thecurrent mode is normal then the button pressed will either be to createor edit an event or to enter focus mode. If the button is to create oredit an event then the user interface provides the appropriate screen(s)and interface to create a new event or edit a current event. If thebutton selected is to enter the focus mode then, with reference to theflowchart in FIG. 5D, the user may (at 522, 524) either set a timer orstay in focus mode until stopped (i.e., until the event ends or theapplication is stopped). As noted above, the planner 220 essentiallycreates a new (ad hoc) event with a start time corresponding to thecurrent time and with an end time being either set by the user or leftopen (or set to the start time of the next event in the user's eventlist 400). The device status for this ad hoc event is set to “focused.”If the user sets a focus timer (at 526), then the user interface of theplanner 220 may provide the user with an interface that allows/enablesthe user to set a duration or end time for the focus mode. The time setby the user is used to set the event end time (although preferably thead hoc event cannot end after the start time of the next event in theuser's event list.

The device is set to focus mode (at 528).

For the processing when the current mode is “focused” (at 520 in FIG.5C): either the user pressed a “STOP” button to end the focus or someother key. First the device checks (at 530) whether the user set an endtime for the current focus event. If no end time was set then the usermay exit the focus mode (at 532). If the current time is in an eventtime then the device mode is set to the mode of the current event (at532).

If an event end time was set and the user pressed the button during theevent time then the planner application 220 warns the user and may stayin the focused mode (at 534). If the user repeats the button press (at536, to leave the focused mode) then the device may leave the focusedmode (at 538). In some embodiments the device may leave the focused modefor a short period of time (e.g., 2 minutes, 5 minutes, etc.) and thenresume in focused mode if not yet at the end of the focused mode for thecurrent event. It should be appreciated that other “termination” optionsare possible and contemplated herein. For example, as noted earlier, insome embodiments the user may be required to enter a password or key inorder to terminate the focused mode. In some embodiments the user may berequired to press the “stop” button or a combination of buttons morethan once in order to exit the focused mode. In some embodiments asingle press of the “stop” button may be sufficient to exit the focusedmode.

At any time, regardless of the mode of the device, the user may alwayshave access to emergency features (e.g., “911” dialing and the like). Nomatter how strict the focus mode, a device's emergency features arenever turned off.

Driving

The dangers of texting while driving are well known, and there is a needfor some way of discouraging texting and other mobile device uses whiledriving. The inventor has realized that driving a vehicle is a kind ofevent that requires focus, albeit more focus than required when studyingor reading.

As noted above, a device may have more than one “focus” state, and thefocus states may have different degrees of restriction on device use.

Accordingly, in some embodiments hereof, the focus application(s) 226may include focused driving application(s)/mechanism(s) 222 that may usedriving data 210 (see FIG. 2). The focus application(s)/mechanism(s) 226may include either or both the focused drivingapplication(s)/mechanism(s) 222 and the plannerapplication(s)/mechanism(s) 220. For the remainder of this descriptionthe planner 220 and the focused driving app 222 are described together,although those of ordinary skill in the art will realize and appreciate,upon reading this description, that either the focused drivingapplication(s)/mechanism(s) 222 or the plannerapplication(s)/mechanism(s) 220 may be present without the other. Inother words, the focus application(s)/mechanism(s) 226 of particularembodiments hereof may include only the focused drivingapplication(s)/mechanism(s) 222 or only the plannerapplication(s)/mechanism(s) 220.

In presently preferred embodiments hereof a user enters the focuseddriving mode by pressing a driving mode button presented on the userinterface by the focused driving application(s)/mechanism(s) 222. Anexample interface is shown in FIG. 6A-6I, and the button processing(540) is described with reference to the flowchart in FIG. 5F.

When a button is pressed, first focus application(s) 226 determines thecurrent mode of the device (at 542). If the device is in normal(non-focused) mode then the button/key is processed at 544 (see FIG.5G), if the device is in event-focused mode then the button/key isprocessed at 546 (similar to the processing at 520 in FIG. 5C). Ifbutton/key is pressed while in driving-focused mode then the button/keyis processed at 548.

With reference to the flowchart in FIG. 5G, showing processing of akey/button while in the normal (or idle) mode: if the “DRIVE” button wasselected (at 550) then the device is set to drive focus mode (at 552),otherwise, if the “FOCUS” (not driving) button was selected (at 554)then the device is set to focus mode (not driving), otherwise some otherkey or button was selected and is processed (at 556). Note that drivefocus mode corresponds to the “focus (driving)” state of FIG. 3, whereas“focus mode (not driving)” corresponds to the “focus (event)” state ofFIG. 3.

With reference now to the flowchart in FIG. 5H, if the user selectsdrive mode then the device can either be set to stay in drive mode for aperiod of time or until stopped (at 558). If the user selects (at 558)to stay in drive mode until stopped then the device is set to drivefocus mode (at 560). If the user selects (at 558) to set a drive timethen the user may set the drive time (at 562) and then the device is setto drive focus mode (at 560). The drive time, if set, may be set as anactual time or as a duration. In either case, the application may createa new event with a start time of the current time and an appropriate endtime (depending on the user's selection). If the end time is left open(i.e., the device is set to drive focused until stopped) then the endtime may be set to a time in the future that will not be reached beforethe vehicle is actually stopped (e.g., 1 day). In such case the devicewill not switch modes based on other future events in the user's eventlist. For example, if the current time is 1 PM and the user enters“drive focused” mode, until stopped, and the user has an event in herevent list at 1:30 PM (to 2:30 PM) with a status of “event focused”,then if the user is still driving at 1:31 PM then the device shouldpreferably stay in “drive focused” mode and not switch to “eventfocused.” If the user ends drive mode before 2:30 PM (during the eventtime) then the device should preferably enter the “event focused” modecorresponding to the 1:30 to 2:30 PM event.

In preferred embodiments hereof the device stays in drive mode untilstopped, and the timer option is not provided.

To set the device into drive focus mode (at 560) the device is set tothe restrictions corresponding to the “focus (driving)” state. Underthese restrictions the device is preferably set to a “do not disturb”state where the user does not receive notifications of incoming messages(e.g., texts) or phone calls and the user cannot send any texts ormessages or use any applications or make any outgoing calls (except foremergency calls). In some embodiments the focused driving applicationmay provide the user with a way to set up and maintain a list ofacceptable parties for which incoming phone call notifications may bereceived. For example, a user may put her parents on such a list so thatthe user will be notified of incoming calls from her parents whiledriving.

In some embodiments the focused driving application, in focused mode,may allow incoming and outgoing voice calls via Bluetooth® connectionsor the like. In this manner, even in focused driving mode the user maybe able to have voice calls with certain parties when a device (e.g., aphone) is connected to a vehicle's Bluetooth® system (supporting hand'sfree conversation). These calls may still be limited to a pre-storedlist of acceptable parties. In these embodiments, even if audioconnections are supported when in focused driving mode.

In some embodiments a user may override the drive-focused mode, e.g., byentering a key or passphrase or the like. This override may be temporaryand will allow the user or a passenger to use the device even though thedevice is being used while driving.

Exemplary operation of the focused driving application is described herewith reference to the flowchart in FIG. 5I In focused driving mode theapplication determines (at 562) if the drive time has ended (e.g., bycomparing the current time to the end time for the current drivingevent). If the drive time has ended then (at 562) the device is set (at564) to normal (non-focus mode) or, if during an event time, then to themode corresponding to that event. If no drive time was set (e.g., theuser chose to stay in drive focused mode until stopped), then thefocused driving application determines (at 566) whether a key or buttonwas pressed, and, if so, processes the key/button (at 568).

With reference now to the flowchart in FIG. 5J, when the user selects akey or button while in focused driving mode, if the user selected an“Emergency” button (at 570) then the device goes into an emergency mode(at 572). If the user did not select an “Emergency” button or key, thenthe device tries to determine (at 574) whether the vehicle has stopped.The device may use hardware (e.g., sensors) and software built in to thedevice (e.g., accelerometers, GPS devices, etc.) to determine if thedevice is in motion. This information may be used to determine if thevehicle is in motion. In some embodiments hereof a vehicle is consideredto be “stopped” (i.e., not driving) if it is substantially stationaryfor some predetermined period of time (e.g., 30 seconds, 1 minute, 90seconds, etc.). This means that a vehicle that is briefly andtemporarily stopped (e.g., in traffic or at a stop street) may not beconsidered “stopped” for the purposes of the focused drivingapplication. Thus, as used herein, the condition of a vehicle being“stopped” may require that the vehicle not be moving for a period oftime. In some cases, if the device resumes motion after being stopped,the motion may correspond to walking and not driving. The system may usesensors in the device (e.g., accelerometers and the like) to determineif the motion and speed of the device corresponds to walking rather thandriving, and the device mode may be set accordingly.

If the vehicle is determined (at 574) to be stopped, then theapplication determines (at 576) whether the user pressed a “Stop” button(to terminate the focused-driving mode). If so (then the vehicle isstopped and the user pressed the “Stop” button) then (at 578) theapplication turns off the focused driving mode (the device is set tonormal (non-focus mode) or, if during an event time, then to the modecorresponding to that event, similar to the processing at 564).

If (at 574) it is determined that the vehicle is not stopped then (at580), regardless of what button or key was pressed, the device warns theuser and stays in focused driving mode.

Tracking and Reporting

Embodiments hereof may include tracking and/or reporting mechanisms thatmay be used to keep track of a device's modes, e.g., by time andlocation. For example, the focus application(s) 226 may store (in focusdata 228) the device's modes (e.g., “Normal”, “Event Focused”, “DrivingFocused”) by start and end time and by start and end location. The focusapplication(s) 226 may then report this information, e.g., by email orby posting it to another computer. In preferred embodiments the storeddata may be locked to prevent unauthorized access, includingunauthorized deletion.

Using the store/report feature, a user's focus information may bereported, e.g., to their parents. For example, a user's parents may beable to tell whether she was driving focused or whether the device wasswitched to normal mode while the user was driving.

User Interface

As described above, the focus application(s)/mechanism(s) 226, includingthe planner 220 and driving app 222, provide a user interface (UI),using, e.g., the UI application(s)/mechanism(s) 216. The UI ispreferably appropriate for the computer device, so that the UI presentedon a laptop computer may differ in form from the UI presented on amobile phone.

A UI may be implemented, at least in part, on a device 100 using UIapplication(s) 216 on that device, and preferably uses the device'sdisplay(s) and input/interaction mechanism(s) (e.g., 114, FIG. 1C). Useof a UI may require selection of items, navigation between views, andinput of information. Different devices may support different techniquesfor presentation of and user interaction with the UI. For example, adevice with an integrated touch screen (e.g., device 100 a as shown inFIG. 1A) may display UI information on the touch screen 102, and acceptuser input (for selection, input, etc.) using the touch screen (e.g.,with a software/virtual keyboard—VKB—for some types of input). A devicewith an integrated screen, keyboard, and mouse (e.g., device 100 b asshown in FIG. 1B) may display UI information on the screen 104, andaccept user input using the hardware keyboard 106 and hardware mouse108. If the screen/display 104 is also a touch screen display, then userinteractions with the UI may use the screen instead of or in addition tothe keyboard 106 and mouse 108. A device with separate components (e.g.,some instances of device 100 c of FIG. 1C) may display UI information onthe display 112 and accept user input to the UI using input/interactionmechanism(s) 114 (e.g., the keyboard 116 and/or mouse 118 and/or gesturemechanism 120). The system hereof is not limited by the manner in whichthe UI is presented or implemented or by the manner in which user inputis determined and made.

Example UI/UX

FIGS. 6A to 6I are example screenshots of aspects of a graphical userinterface according to exemplary embodiments hereof, showing anexemplary UI and corresponding UX. FIG. 6A depicts a storyboard showingan exemplary UI for a focus app 226 that includes a planner 220 and adriving app 222. FIGS. 6B to 6I depicts some of the screens of FIG. 6Ain greater detail.

As should be appreciated, the UI/UX shown in FIGS. 6B to 6I is merely anexample, and different and/or other interface features are contemplatedherein. In preferred implementations the driving (and other focus) modesare controlled via a control panel integrated into the device's OS. Forexample, as discussed below, in some exemplary embodiments hereof, thedriving mode may be turned on and off using the control panel shown inFIGS. 6J and 6K.

Those of ordinary skill in the art will realize and appreciate, uponreading this description, that integrating the driving (or other focus)application into the device's OS allows for levels of control that maynot be available to all applications running on the device. Inparticular, integrating the application with the device's OS and givingaccess via the device's control panel allows the focus (e.g., driving)application to control aspects of at least some integrated applicationson the device. The integrated applications may include the chatapplication, the cellular communications applications, etc.

Implementation

Computing

The applications, services, mechanisms, operations and acts shown anddescribed above are implemented, at least in part, by software runningon one or more computers or computer systems or user devices (e.g.,devices 100 a, 100 b, 100 c in FIGS. 1A-1C, respectively). It should beappreciated that each user device is, or comprises, a computer system.

Programs that implement such methods (as well as other types of data)may be stored and transmitted using a variety of media (e.g., computerreadable media) in a number of ways. Hard-wired circuitry or customhardware may be used in place of, or in combination with, some or all ofthe software instructions that can implement the processes of variousembodiments. Thus, various combinations of hardware and software may beused instead of software only.

One of ordinary skill in the art will readily appreciate and understand,upon reading this description, that the various processes describedherein may be implemented by, e.g., appropriately programmed generalpurpose computers, special purpose computers and computing devices. Oneor more such computers or computing devices may be referred to as acomputer system.

FIG. 7 is a schematic diagram of a computer system 700 upon whichembodiments of the present disclosure may be implemented and carriedout.

According to the present example, the computer system 700 may include abus 702 (i.e., interconnect), one or more processors 704, one or morecommunications ports 714, location device(s) 715, a main memory 706,optional removable storage media 710, read-only memory 708, and a massstorage 712. Communication port(s) 714 may be connected to one or morenetworks (e.g., computer networks, cellular networks, etc.) by way ofwhich the computer system 700 may receive and/or transmit data. Thelocation device(s) 715 may include GPS devices and the like that can beused to determine the location of the device.

As used herein, a “processor” means one or more microprocessors, centralprocessing units (CPUs), computing devices, microcontrollers, digitalsignal processors, or like devices or any combination thereof,regardless of their architecture. An apparatus that performs a processcan include, e.g., a processor and those devices such as input devicesand output devices that are appropriate to perform the process.

Processor(s) 704 can be (or include) any known processor, such as, butnot limited to, an Intel® Itanium® or Itanium 2® processor(s), AMD®Opteron® or Athlon MP® processor(s), or Motorola® lines of processors,and the like. Communications port(s) 714 can be any of an RS-232 portfor use with a modem based dial-up connection, a 10/100 Ethernet port, aGigabit port using copper or fiber, or a USB port, and the like.Communications port(s) 714 may be chosen depending on a network such asa Local Area Network (LAN), a Wide Area Network (WAN), a ContentDelivery Network (CDN), or any network to which the computer system 700connects. The computer system 700 may be in communication withperipheral devices (e.g., display screen 716, input device(s) 718) viaInput/Output (I/O) port 720. Some or all of the peripheral devices maybe integrated into the computer system 700, and the input device(s) 718may be integrated into the display screen 716 (e.g., in the case of atouch screen).

Main memory 706 can be Random Access Memory (RAM), or any other dynamicstorage device(s) commonly known in the art. Read-only memory 708 can beany static storage device(s) such as Programmable Read-Only Memory(PROM) chips for storing static information such as instructions forprocessor(s) 704. Mass storage 712 can be used to store information andinstructions. For example, hard disks such as the Adaptec® family ofSmall Computer Serial Interface (SCSI) drives, an optical disc, an arrayof disks such as Redundant Array of Independent Disks (RAID), such asthe Adaptec® family of RAID drives, or any other mass storage devicesmay be used.

Bus 702 communicatively couples processor(s) 704 with the other memory,storage and communications blocks. Bus 702 can be a PCI/PCI-X, SCSI, aUniversal Serial Bus (USB) based system bus (or other) depending on thestorage devices used, and the like. Removable storage media 710 can beany kind of external hard-drives, Compact Disc-Read Only Memory(CD-ROM), Compact Disc-Re-Writable (CD-RW), Digital Versatile Disk-ReadOnly Memory (DVD-ROM), etc.

Embodiments herein may be provided as one or more computer programproducts, which may include a machine-readable medium having storedthereon instructions, which may be used to program a computer (or otherelectronic devices) to perform a process. As used herein, the term“machine-readable medium” refers to any medium, a plurality of the same,or a combination of different media, which participate in providing data(e.g., instructions, data structures) which may be read by a computer, aprocessor or a like device. Such a medium may take many forms, includingbut not limited to, non-volatile media, volatile media, and transmissionmedia. Non-volatile media include, for example, optical or magneticdisks and other persistent memory. Volatile media include dynamic randomaccess memory, which typically constitutes the main memory of thecomputer. Transmission media include coaxial cables, copper wire andfiber optics, including the wires that comprise a system bus coupled tothe processor. Transmission media may include or convey acoustic waves,light waves and electromagnetic emissions, such as those generatedduring radio frequency (RF) and infrared (IR) data communications.

The machine-readable medium may include, but is not limited to, floppydiskettes, optical discs, CD-ROMs, magneto-optical disks, ROMs, RAMs,erasable programmable read-only memories (EPROMs), electrically erasableprogrammable read-only memories (EEPROMs), magnetic or optical cards,flash memory, or other type of media/machine-readable medium suitablefor storing electronic instructions. Moreover, embodiments herein mayalso be downloaded as a computer program product, wherein the programmay be transferred from a remote computer to a requesting computer byway of data signals embodied in a carrier wave or other propagationmedium via a communication link (e.g., modem or network connection).

Various forms of computer readable media may be involved in carryingdata (e.g. sequences of instructions) to a processor. For example, datamay be (i) delivered from RAM to a processor; (ii) carried over awireless transmission medium; (iii) formatted and/or transmittedaccording to numerous formats, standards or protocols; and/or (iv)encrypted in any of a variety of ways well known in the art.

A computer-readable medium can store (in any appropriate format) thoseprogram elements that are appropriate to perform the methods.

As shown, main memory 706 is encoded with application(s) 722 thatsupport(s) the functionality as discussed herein (an application 722 maybe an application that provides some or all of the functionality of oneor more of the mechanisms described herein). Application(s) 722 (and/orother resources as described herein) can be embodied as software codesuch as data and/or logic instructions (e.g., code stored in the memoryor on another computer readable medium such as a disk) that supportsprocessing functionality according to different embodiments describedherein.

For example, as shown in FIG. 2, application(s) 722 may include deviceapplications 200). As shown, e.g., in FIG. 2, device application(s) 200may include system/administrative application(s) 214, user interface(UI) application(s) 216, storage application(s) 218, planningapplication(s) 220, focused driving application(s) 222, and othermiscellaneous application(s) 224.

During operation of one embodiment, processor(s) 704 accesses mainmemory 706, e.g., via the use of bus 702 in order to launch, run,execute, interpret or otherwise perform the logic instructions of theapplication(s) 722. Execution of application(s) 722 produces processingfunctionality of the service(s) or mechanism(s) related to theapplication(s). In other words, the process(es) 724 represents one ormore portions of the application(s) 722 performing within or upon theprocessor(s) 704 in the computer system 700.

For example, process(es) 724 may include device process(es)corresponding to one or more of the device application(s) 722.

It should be noted that, in addition to the process(es) 724 thatcarries(carry) out operations as discussed herein, other embodimentsherein include the application 722 (i.e., the un-executed ornon-performing logic instructions and/or data). The application 722 maybe stored on a computer readable medium (e.g., a repository) such as adisk or in an optical medium. According to other embodiments, theapplication 722 can also be stored in a memory type system such as infirmware, read only memory (ROM), or, as in this example, as executablecode within the main memory 706 (e.g., within Random Access Memory orRAM). For example, application 722 may also be stored in removablestorage media 710, read-only memory 708, and/or mass storage device 712.

Those skilled in the art will understand that the computer system 700can include other processes and/or software and hardware components,such as an operating system that controls allocation and use of hardwareresources.

As discussed herein, embodiments of the present invention includevarious steps or operations. A variety of these steps may be performedby hardware components or may be embodied in machine-executableinstructions, which may be used to cause a general-purpose orspecial-purpose processor programmed with the instructions to performthe operations. Alternatively, the steps may be performed by acombination of hardware, software, and/or firmware. The term “module”refers to a self-contained functional component, which can includehardware, software, firmware or any combination thereof.

One of ordinary skill in the art will readily appreciate and understand,upon reading this description, that embodiments of an apparatus mayinclude a computer/computing device operable to perform some (but notnecessarily all) of the described process.

Embodiments of a computer-readable medium storing a program or datastructure include a computer-readable medium storing a program that,when executed, can cause a processor to perform some (but notnecessarily all) of the described process.

Where a process is described herein, those of ordinary skill in the artwill appreciate that the process may operate without any userintervention. In another embodiment, the process includes some humanintervention (e.g., a step is performed by or with the assistance of ahuman).

Integration

As should be appreciated, a so-called smartphone or cellular phone isessentially a mobile computing device, and the features, applicationsand mechanisms described herein may be implemented as mechanisms (e.g.,software and/or hardware) running on such devices. Thus, e.g., thedriving application may be an application running on a smartphone (e.g.,an Android or an iPhone® or the like). Those of ordinary skill in theart will realize and appreciate, upon reading this description, thatvarious aspects of the applications, including, specifically the focusapplications, may be integrated into the operating system of thecomputing device. For example, the focused driving application may beintegrated into the Google Android and Apple's iOS operating systems (OSs) (“iOS” refers to an operating system used for mobile devicesmanufactured by Apple Inc., “Android” is a mobile OS based on the Linuxkernel and currently developed by Google, Inc.)

Such integration will enable the applications to run more efficientlyand may allow them to take advantage of and possibly control lower-leveloperating system features. If the driving application is integrated intothe OS of a device then the user may be able to set the application'susage preferences via the device's control panel (e.g., as shown inFIGS. 6J-6K).

The focus application(s) may need to access features of the underlyingOS via APIs provided by the device manufacturer. For example, in orderto disable notifications or outgoing text messages, or to prevent use ofvarious applications, the focus applications may require access to thedevice's APIs or to APIs not normally provided to applications providedby outside entities (i.e., by application developers other than thedevice manufacturer or OS provider).

In some aspects, the driving application may be integrated into the OSand turned on and off via a switch (e.g., a “Driving” mode switch, FIGS.6J-6K) in the control panel (similar to the switch used to put a deviceinto so-called “Airplane mode”). As shown in FIG. 6J, the device'scontrol panel provides a switch (labeled “Driving mode”) to turn on thedriving application features. FIG. 6K shows the device's control panelwith the “Driving Mode” turned on. As shown in FIG. 6K, with the drivingmode turned on, the device may indicate that it is in driving mode(e.g., by an icon in the top left) as well as by notifying the user thatthe device is in “Cellular Driving Mode.” A device configured accordingto exemplary embodiments hereof will also preferably include the“Airplane” mode switch (not shown in the drawings).

Vehicle Integration

Many vehicle manufacturers have integrated smartphone and other cellularfunctionality into vehicles. The focus application(s) described hereinmay be fully or partially integrated into vehicles to control some orall of the integrated smartphone functionality. When the focusapplication is integrated into a vehicle, in some embodiments, the focusapplication may be turned on when the vehicle is driving.

Many vehicles support device connectivity, whereby a smartphone or thelike may connect to a cars audio system (e.g., using Bluetooth®). Insome exemplary embodiments hereof, the driving application in a phonemay be turned on automatically when the phone connects to a car'sBluetooth® system. When connected via a vehicle's Bluetooth® system, thedriving application may allow cellular telephone calls while disablingor limiting other features (e.g., as described above).

In some other embodiments hereof a user may configure the drivingapplication to selectively turn on automatically when the phone connectsto a car's Bluetooth® system. Preferably the driving application in aphone will only be automatically turned on when it connects to theBluetooth® system to which the phone has previously connected.

Although aspects of vehicle integration are described with respect tothe Bluetooth® protocol, those of ordinary skill in the art will realizeand appreciate, upon reading this description, that different and/orother protocols may be used.

Those of ordinary skill in the art will realize and appreciate, uponreading this description, that the driving and focus mode switches andthe driving and focus applications allow a device user to quickly putthe device in an appropriate mode (e.g., driving and/or focused) withouthaving to selectively adjust the device's settings each time a modechange is desired.

As used in this description, the term “portion” means some or all. So,for example, “A portion of X” may include some of “X” or all of “X”. Inthe context of a conversation, the term “portion” means some or all ofthe conversation.

As used herein, including in the claims, the phrase “at least some”means “one or more,” and includes the case of only one. Thus, e.g., thephrase “at least some ABCs” means “one or more ABCs”, and includes thecase of only one ABC.

As used herein, including in the claims, the phrase “based on” means“based in part on” or “based, at least in part, on,” and is notexclusive. Thus, e.g., the phrase “based on factor X” means “based inpart on factor X” or “based, at least in part, on factor X.” Unlessspecifically stated by use of the word “only”, the phrase “based on X”does not mean “based only on X.”

As used herein, including in the claims, the phrase “using” means “usingat least,” and is not exclusive. Thus, e.g., the phrase “using X” means“using at least X.” Unless specifically stated by use of the word“only”, the phrase “using X” does not mean “using only X.”

In general, as used herein, including in the claims, unless the word“only” is specifically used in a phrase, it should not be read into thatphrase.

As used herein, including in the claims, the phrase “distinct” means “atleast partially distinct.” Unless specifically stated, distinct does notmean fully distinct. Thus, e.g., the phrase, “X is distinct from Y”means that “X is at least partially distinct from Y,” and does not meanthat “X is fully distinct from Y.” Thus, as used herein, including inthe claims, the phrase “X is distinct from Y” means that X differs fromY in at least some way.

As used herein, including in the claims, a list may include only oneitem, and, unless otherwise stated, a list of multiple items need not beordered in any particular manner Unless specifically stated otherwise, alist may include duplicate items. For example, as used herein, thephrase “a list of XYZs” may include one or more “XYZs”.

It should be appreciated that the words “first” and “second” in thedescription and claims are used to distinguish or identify, and not toshow a serial or numerical limitation. Similarly, words such as“particular,” “specific,” “certain,” and “given” if used, are todistinguish or identify within a claim and are not intended to beotherwise limiting. Furthermore, letter labels (e.g., “(B)”, “(C)”,“(D)”, and so on, or “(a)”, “(b)”, and so on) and/or numbers (e.g.,“(i)”, “(ii)”, and so on) if in the claims, are used to assist inreadability, and are not intended to be otherwise limiting or to imposeany serial or numerical limitations or orderings.

No ordering is implied by any of the labeled boxes in any of the flowdiagrams unless specifically shown and stated. When disconnected boxesare shown in a diagram the activities associated with those boxes may beperformed in any order, including fully or partially in parallel.

Thus are described methods, devices and systems supporting focuseddriving, working, and studying without distraction. While the inventionhas been described in connection with what is presently considered to bethe most practical and preferred embodiments, it is to be understoodthat the invention is not to be limited to the disclosed embodiment, buton the contrary, is intended to cover various modifications andequivalent arrangements included within the spirit and scope of theappended claims.

I claim:
 1. A communication device comprising: one or more processorsand one or more memories supporting communication, said devicecomprising a plurality of modes, including a normal mode and a drivingmode, wherein said normal mode is distinct from said driving mode, andwherein, when said device is in said driving mode one or more featuresof said device are at least partially disabled, and wherein the one ormore features of said device that are at least partially disabled in thedriving mode include one or more features relating to communicationsupported by the device, wherein the device is configured to: (a) trackparticular information about at least some of said device's modes by oneor more of (i) time, and (ii) location; and (b) report at least some ofsaid particular information about said device's modes to at least onelocation off the device.
 2. The device of claim 1, wherein said deviceis configured to: track said particular information about said device'smodes by one or more of (i) start time, (ii) end time, (iii) startlocation, and (iv) end location.
 3. The device of claim 1, wherein saidat least some of said particular information about said device's modesis reported by one or more of: (i) sending said at least some of saidparticular information by electronic mail, and (ii) sending said atleast some of said particular information to another computer.
 4. Thedevice of claim 1, wherein particular information about said device'smodes is usable to determine when the device was in driving mode.
 5. Thedevice of claim 1, wherein said certain information is locked on saiddevice.
 6. The device of claim 1, wherein unauthorized access to saidcertain information on said device is prevented.
 7. The device of claim1, wherein, in the driving mode, emergency features of the device arenot disabled.
 8. The device of claim 1, wherein said one or moreprocessors and one or more memories supporting communication supportwireless communication.
 9. The device of claim 8, wherein said wirelesscommunication comprises cellular communication.
 10. The device of 9,wherein the one or more features of said device that are at leastpartially disabled in the driving mode include one or more of: (A)notifications of one or more incoming calls; (B) notifications of one ormore incoming messages; (C) one or more outgoing calls; and (D) one ormore applications on said device.
 11. The device of claim 10, whereinthe one or more applications on the device comprise one or more of: oneor more social networking applications; one or more textingapplications; one or more browser applications; one or more messagingapplications; one or more conferencing applications; and one or morephotography applications.
 12. The device of claim 1, wherein the deviceis further configured to: (c) allow selection and de-selection of saiddriving mode.
 13. The device of claim 12, wherein said device isconfigured to support selection and de-selection of said driving modevia a user interface (UI).
 14. The device of claim 13, wherein said userinterface comprises a control panel of said device.
 15. The device ofclaim 14, wherein said control panel is a system control panel.
 16. Thedevice of claim 15, wherein said control panel is integrated into anoperating system (OS) of the device.
 17. The device of claim 16, whereinsaid control panel comprises a switch to selectively set said deviceinto or out of said driving mode.
 18. The device of claim 1, wherein,when in said driving mode, said device indicates that said device is indriving mode.
 19. The device of claim 18, wherein, when in said drivingmode, said device indicates that said device is in driving mode by anicon on a display.
 20. The device of claim 1, wherein said devicecomprises a cellular phone.
 21. The device of claim 1, wherein saiddevice is at least partially integrated into a vehicle.
 22. The deviceof claim 1, wherein said device enters said driving mode when saiddevice connects to a vehicle.
 23. The device of claim 22, wherein saiddevice automatically enters said driving mode when said device connectsto a vehicle to which the device has previously connected.
 24. Anon-transitory computer-readable medium with one or more computerprograms stored therein that, when executed by one or more processors ofa device, said device comprising a plurality of modes, including anormal mode and a driving mode, cause the one or more processors toperform at least the operations of: (A) tracking particular informationabout at least some of said device's modes by one or more of (i) time,and (ii) location; and (B) reporting at least some of said particularinformation about said device's modes to at least one location off thedevice, wherein said normal mode is distinct from said driving mode, andwherein, when said device is in said driving mode one or more featuresof said device are at least partially disabled, and wherein the one ormore features of said device that are at least partially disabled in thedriving mode include one or more features relating to communicationsupported by the device.
 25. The non-transitory computer-readable mediumof claim 24, wherein said tracking in (A) tracks said particularinformation about said device's modes by one or more of: (i) start time,(ii) end time, (iii) start location, and (iv) end location.
 26. Thenon-transitory computer-readable medium of claim 24, wherein said atleast some of said particular information about said device's modes isusable to determine when the device was in driving mode.
 27. Thenon-transitory computer-readable medium of claim 24, wherein saidcertain information on said device is locked.
 28. The non-transitorycomputer-readable medium of claim 24, wherein unauthorized access tosaid certain information on said device is prevented.
 29. Thenon-transitory computer-readable medium of claim 24, wherein said atleast some of said particular information about said device's modes isreported in (B) by one or more of: (i) sending said at least some ofsaid particular information by electronic mail, and (ii) sending said atleast some of said particular information to another computer.
 30. Thenon-transitory computer-readable medium of claim 29, wherein said atleast some tracked information about said device's modes is reported byone or more of: (i) sending said information by electronic mail, and(ii) sending said information to another computer.
 31. Thenon-transitory computer-readable medium of claim 24, wherein said devicesupports wireless communication.
 32. The non-transitorycomputer-readable medium of claim 31, wherein said wirelesscommunication comprises cellular communication.
 33. The non-transitorycomputer-readable medium of claim 32, wherein the one or more featuresof said device that are at least partially disabled in the driving modeinclude one or more of: (A) notifications of one or more incoming calls;(B) notifications of one or more incoming messages; (C) one or moreoutgoing calls; and (D) one or more applications on said device.
 34. Thenon-transitory computer-readable medium of claim 33, wherein the one ormore applications on the device comprise one or more of: one or moresocial networking applications; one or more texting applications; one ormore browser applications; one or more messaging applications; one ormore conferencing applications; and one or more photographyapplications.
 35. The non-transitory computer-readable medium of claim24, wherein the one or more computer programs further cause the one ormore processors to perform at least the operations of: (C) allowingselection and de-selection of said driving mode.
 36. The non-transitorycomputer-readable medium of claim 35, wherein selection and de-selectionof said driving mode are via a user interface (UI).
 37. Thenon-transitory computer-readable medium of claim 36, wherein said userinterface comprises a control panel of said device.
 38. Thenon-transitory computer-readable medium of claim 37, wherein saidcontrol panel is a system control panel.
 39. The non-transitorycomputer-readable medium of claim 37, wherein said control panel isintegrated into an operating system (OS) of the device.
 40. Thenon-transitory computer-readable medium of claim 37, wherein saidcontrol panel comprises a switch to selectively set said device into orout of said driving mode.
 41. The non-transitory computer-readablemedium of claim 24, wherein, when in said driving mode, said deviceindicates that said device is in driving mode.
 42. The non-transitorycomputer-readable medium of claim 41, wherein, when in said drivingmode, said device indicates that said device is in driving mode by anicon on a display associated with the device.
 43. The non-transitorycomputer-readable medium of claim 24, wherein said device comprises acellular phone.
 44. The non-transitory computer-readable medium of claim24, wherein said device is at least partially integrated into a vehicle.45. The non-transitory computer-readable medium of claim 24, whereinsaid device enters said driving mode when said device connects to avehicle to which the device has previously connected.
 46. A cellulartelephone device comprising: one or more processors and one or morememories supporting wireless communication, including cellularcommunication, said device comprising a plurality of modes, including anormal mode and a driving mode, wherein said normal mode is distinctfrom said driving mode, and wherein, when said device is in said drivingmode one or more features of said device are at least partiallydisabled, and wherein the one or more features of said device that areat least partially disabled in the driving mode include one or morefeatures relating to communication supported by the device, wherein thedevice is configured to: (a) track certain information about when saiddevice is in said driving mode, wherein said certain information istracked by one or more of (i) time, and (ii) location; and (b) report atleast some certain information to at least one location off the device.47. The device of claim 46, wherein said certain information about isusable off said device to determine when the device was in driving mode.48. The device of claim 47, wherein said certain information about saiddevice's modes is locked on said device.
 49. The device of claim 47,wherein unauthorized access to said certain information is prevented.50. The device of claim 46, wherein the one or more features of saidcellular telephone device that are at least partially disabled in thedriving mode include one or more of: (A) notifications of one or moreincoming calls; (B) notifications of one or more incoming messages; (C)one or more outgoing calls; and (D) one or more applications on saiddevice.
 51. The device of claim 50, wherein the one or more applicationson the device comprise one or more of: one or more social networkingapplications; one or more texting applications; one or more browserapplications; one or more messaging applications; one or moreconferencing applications; and one or more photography applications. 52.The device of claim 46, wherein the device is further configured to: (c)allow selection and de-selection of said driving mode.
 53. The device ofclaim 46, wherein selection and de-selection of said driving mode arevia a user interface (UI).
 54. The device of claim 53, wherein said userinterface comprises a control panel of said device.
 55. The device ofclaim 54, wherein said control panel is a system control panel.
 56. Thedevice of claim 54, wherein said control panel is integrated into anoperating system (OS) of the device.
 57. The device of claim 54, whereinsaid control panel comprises a switch to selectively set said deviceinto or out of said driving mode.